home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
doors_2
/
rnet107u.zip
/
SAMPLE1.CFG
< prev
next >
Wrap
Text File
|
1991-01-03
|
13KB
|
262 lines
;=============================== SAMPLE1.CFG =================================
;
; This is a sample host configuration file. If you will be using this as a
; starting point for your configuration, copy or rename this file to the
; HOST_ID of your intended host system. (HOST_ID.CFG)
;
; This sample is generally configured for Faster-Than-Light. If this
; configuration were to be used for Faster-Than-Light, you would need to
; rename it to FTL.CFG (FTL being the HOST_ID).
;
; After each keyword assignment, a description is given explaining it.
; Lines with ;'s at the beginning are ignored by RNet as are blank lines.
;
; Note that not all keywords are used in this sample, only those keywords
; which are most common or are required for operation. Keywords such as
; TCAN, PRIVATE_USER, and ARCHIVE=EXTERNAL are not shown since their use is
; rare. See LOWMEM.BAT for information on ARCHIVE=EXTERNAL.
;
; Please read the documentation, "Configuration Files; Keywords: ..." for
; more information on these and other keywords.
;
; If the default setting of any given keyword is acceptable, you need not
; include that keyword in the configuration file. The default is noted
; (usually with an * next to the YES/NO) for most keywords for your ease of
; deletion of unnecessary keywords.
;
;============================= Users and Names ===============================
HOSTSYSOP=ROBERT VOSTREYS
; Specify the real name of your host Sysop. Any messages addressed to/from
; "SYSOP" on the host system will be changed to the specified name when
; imported here (locally).
LOCALSYSOP=YOUR NAME HERE
; Specify your real name (or your name as it should appear on other systems).
; Any messages addressed to/from "SYSOP" leaving your system will be changed
; to use this name.
MAKESYSOP=NO
; YES = change incoming messages addressed to the local Sysop to "SYSOP".
; NO*= leave incoming messages addressed to the local Sysop name alone.
HANDLE=SPARKY,MARK HERRING
; Up to 25 "handle" conversions may be specified. This format will translate
; SPARKY to MARK HERRING every time SPARKY is seen in the to/from fields of a
; message. This translation will occur on both import and export processing.
; The reverse is not true.
HANDLE=*RICKY LACY,RICKY LACY - [SYSOP]
; The asterisks ("*") used in this handle statement instructs RNet that you
; wish a two-way translation to occur. The above example might be used by
; RICKY LACY on his board if he wanted his name to appear as RICKY LACY -
; [SYSOP] locally. Since this is not appropriate over the network, this
; translation will convert RICKY LACY to RICKY LACY - [SYSOP] during imports
; and RICKY LACY - [SYSOP] to RICKY LACY during exports.
;
;================================= Taglines ==================================
HTAG0=■ ILink ■ Faster-Than-Light BBS ■ Atlanta GA ■ 404-292-8761
; This statement (or HOSTORIGIN) specifies the default tagline to be placed
; on messages which originate from the host system. Each network has their
; own rules for tagline formatting, so check with them for specifics.
TAG0=■ ILink ■ My BBS Name here ■ My City State here ■ My Phone Number here
; Use TAG0 (or ORIGIN) to specify the tagline which is to be appended
; to messages which originate from your board. Messages entered by you
; or your users will have this tagline appended to them.
HTAG1=■ ByteBrothers ■ FTL ■ Bringing ByteBrothers to Space!
; This is an example of an alternate network tagline (HTAG1 vs HTAG0). This
; tagline will not be used unless RNet is instructed to use it for specific
; conferences. See the CONF= statements below for example use.
TAG1=■ My BBS Name here ■ My cute ByteBrothers phrase here
; Example alternate network tagline (TAG1 vs TAG0) for locally generated
; messages (messages from you or your users in a specified conference will
; have this tagline instead of the TAG0 tagline). See CONF= below.
RTAG=YES
; YES*= Enable the " ■ RNet v.vvx:" header on all taglines.
; NO = Disable the RNet header. hTAGx statements will compose the
; entire tagline text -- nothing additional will be added by RNet.
; [NOTE: This is disabled in the unregistered version of RNet]
; ORIGIN = Instructs RNet to place " * ORIGIN: " at the beginning of all
; taglines. Some network software packages require this specific
; text to be present for proper operation. The RNet v.vv header will
; be added to the end of the tagline instead of the beginning.
FORCETAG=NO
; YES = Instructs RNet to ALWAYS place a tagline on every message.
; NO*= Only place taglines on messages that need them (HOST and LOCAL).
FORCENOTAG=NO
; YES = Instruct RNet to NEVER place a tagline on a message.
; NO*= Only place taglines on messages that need them (HOST and LOCAL).
FIXJH=NO
; YES = Have RNet automatically decrypt John Hancock encrypted taglines.
; NO*= Leave JH taglines encrypted.
;============================ Packet Processing ==============================
COMPRESS=PKZIP -M -EX
; Specify the command (program) and options to execute to compress a REP
; packet for sending to the host. Default = PKZIP -M -EX
UNCOMPRESS=PKUNZIP -O
; Specify the command and options to execute to uncompress incoming QWK
; packets from the host. Default = PKUNZIP -O
WORKDIR=D:\SCRATCH\
; Specify the drive and directory to use for scratch file creation (including
; uncompressed QWK packets). Be sure this drive has enough space to handle
; the largest QWK and/or REP packets you might possibly need to process.
; NOTE: You may also use an environment variable to specify this. Default =
; current drive/directory (RNet knows what to kill and not kill when done).
;
REPLYPROCESS=APPEND
; APPEND = If a REP packet is found during EXPORT processing, uncompress it
; and add additional messages to it. To use this function, your
; mail event MUST delete REP packets after successful uploading!
;OVERWRITE= If a REP packet is found during EXPORT processing, it is deleted
; and overwritten. Note that if you neglect to restore the backup
; pointers if a mail-run failed, and the messages in the REP file
; have not been sent to the host, they will be "lost".
QWKPATH=D:\DOWNLOAD\
; Specify the drive/directory where RNet should look for QWK packets you have
; downloaded from your host. By default, RNet will only look on the current
; drive and directory.
REPPATH=D:\UPLOAD\
; Specify the drive/directory where RNet should build REP packets in
; preparation of being uploaded to your host. This is also where RNet will
; look for a REP file to append to or overwrite. Default: Current drive and
; directory.
KILLQWK=YES
; YES = Have RNet delete QWK packets after successful import processing.
; If anything goes wrong or if RNet gets confused, the QWK packet
; will not be deleted.
; NO*= Leave QWK packets alone -- it is up to you to delete/move them.
CHECKREP=NO
; Have RNet look for a REP packet everytime it starts operation. This does
; not effect the automatic checking done for overwrite or append. Enable
; this keyword if you commonly run RNet outside of your event and you are
; prone to forgetting to delete REP packets after uploading them. RNet,
; when it finds a REP packet, will prompt you to: Delete the REP and
; continue; Retain the REP and abort; or Continue normally. If you do not
; respond in 10 seconds, RNet will continue normally (the REP will not be
; deleted and thus will be appended to or overwritten as per the
; REPLYPROCESS= setting).
CKPOINTERS=YES
; YES*= Check all messagebase pointers against the messagebases at startup.
; NO = Do not check pointers against messagebase pointers at startup.
; It is NOT recommended that you disable the pointer checking!
;============================ Message Processing =============================
PRIVATE=NO
; YES = Allow RNet to pass private (R/O) messages in all conferences.
; NO*= Do not allow RNet to pass private messages in all conferences.
PRIVATECONF=1,2,3,4,5
; Specify the conference(s) that you wish RNet to pass private messages in.
COMMENTS=NO
; YES = In PRIVATECONF conferences, send comment security messages also.
; NO*= Never send comment security messages, even in private conferences.
IGNOREECHO=1,2,3,4,5
; Specify the conference(s) that RNet should ignore the PCBoard 14.x Echo
; status flag in. Use this to force any non-echo messages to be echoed.
;
;========================== Multi-Network Keycode ============================
KEYCODE=%
; See RNET.DOC for more information on the KEYCODE keyword. If you are not
; involved in cross-echoing (having multiple networks or calling multiple
; hosts to pass the same conference(s)), the above setting is fine as is.
;============================= Conference Links ==============================
CONF=1,25 (local conf 1 = host conf 25, use HTAG0 and TAG0 taglines)
CONF=2,26:0 (local conf 2 = host conf 26, use HTAG0 and TAG0 taglines)
CONF=3,27:1 (local conf 3 = host conf 27, use HTAG1 and TAG1 taglines)
CONF=4,16 (AtlSysops)
CONF=5,39 (EchoTest)
; You will need one CONF= statement for each conference you are echoing
; to/from your host. Specify the local conference number (the number of the
; conference on your system), a comma, the host conference number (the number
; of the conference on the host system). Optionally, you may add a colon and
; a number from 0 to 9 specifying which HTAGx and TAGx taglines to use for
; that conference. You may place "comments" after a CONF statement, usually
; showing the conference name for your referance (such as the conferences 4
; and 5 listings above -- AtlSysops is conference 16 and EchoTest is
; conference 39 on FTL).
EXTENDED=NO
; YES = Instruct RNet that the host supports over 255 conferences when RNet
; is having difficulty automatically detecting this.
; NO*= Have RNet automatically detect 32765 conference support.
;=========================== PCBoard Interaction =============================
NODE=3
; Specify the node number executing your daily RNet event. This node number
; is needed by RNet to properly examine the USERNET.DAT file to determine
; from what other users are doing on other nodes which method of message
; insertion it should use (safe or fast). NOTE: Specify 0 if you want RNet
; to use the environment variable NODE= (this is the recommended approach).
USERNET=D:\PCB\MAIN\USERNET.DAT
; Specify the filename used by PCBoard for multinode chat/interaction. RNet
; will "show up" as a user on the node chat display (on the node specified by
; NODE or the environment variable NODE=). RNet will report (via the "city")
; display: Init; Import/Export HOST_ID ConfName; Cleanup; Creating Reports;
; etc. This allows both you and your users to "see" what RNet is doing via
; the NODE CHAT display from within PCBoard/ProDoor.
;
;================================= Reports ===================================
CONFREPORT=D:\PCB\GEN\BLT20
; Specify the filename to use for generation of the conference analysis
; report. Default is to use HOST_ID.RPT in the current directory.
SUPERLOG=D:\SUPERLOG.TXT
; If you want a listing of all messages processed (looks like a Quick scan)
; then specify the filename to use for the SUPERLOG. Be careful as this log
; will grow rather quickly! Useful for GREPping out listings of message
; threads for other analysis programs or user/name tracking.
CALLERLOG=D:\PCB\MAIN\CALLER
; If you wish RNet to log operations to your callers logs, specify the base
; callerlog filename. If you are running a multinode system, RNet will
; automatically append the node number to this filename. The default format
; lists each conference with activity and number of messages processed and
; the processing time.
LONGCALLER=NO
; YES = List EVERY message imported/exported to the callerlog.
; NO*= Use the short (default) format for the callerlog reporting.
;============================= Other Operations ==============================
RUN=PCBCONF D:\PCB\MAIN\CNAMES RNETCONF -i
; RUN statements tell RNet to create a DOS COMMAND.COM shell and execute the
; statement specified. This is useful to force RNet to do something
; everytime it is run. The above example will have RNet run PCBCONF to force
; updating of RNETCONF (the listing of local conferences and messagebase
; locations) everytime RNet is run, just for safety sake.
;=============================================================================